Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7032214222efd936192a9cacfedde0db97d888533861cb978729cb447e457214

Tx prefix hash: 06eb41fe404d018600502a73c8811b871e3753cc4bde193ff78d16f32209d354
Tx public key: 83a6cbbfb4af69cb1e23dd03e5d0a9ca2176bbe49de8ed501f3ef485d99a8c0f
Timestamp: 1703776420 Timestamp [UCT]: 2023-12-28 15:13:40 Age [y:d:h:m:s]: 01:339:12:00:18
Block: 923047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501509 RingCT/type: yes/0
Extra: 0183a6cbbfb4af69cb1e23dd03e5d0a9ca2176bbe49de8ed501f3ef485d99a8c0f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54d7b335495e3c9765e63e5090e1d359abdc8b6c10e6eceeb39f770abd72d4d2 0.600000000000 1380763 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 923057, "vin": [ { "gen": { "height": 923047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d7b335495e3c9765e63e5090e1d359abdc8b6c10e6eceeb39f770abd72d4d2" } } ], "extra": [ 1, 131, 166, 203, 191, 180, 175, 105, 203, 30, 35, 221, 3, 229, 208, 169, 202, 33, 118, 187, 228, 157, 232, 237, 80, 31, 62, 244, 133, 217, 154, 140, 15, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8