Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73f1b0a71cb74246ed2d2aa2c39ca1666327316a9d04db47962d0881e7d22db

Tx prefix hash: 43f4993767d5beea5e7cd2803e20df6b04f898a4079f56003832c68112e9d6b1
Tx public key: 5d3130c02b5e6effced84b140d75c240d4f64e94d5bbf42ec1988b95e4a7fa7f
Timestamp: 1737148137 Timestamp [UCT]: 2025-01-17 21:08:57 Age [y:d:h:m:s]: 00:151:16:42:53
Block: 1199571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108117 RingCT/type: yes/0
Extra: 015d3130c02b5e6effced84b140d75c240d4f64e94d5bbf42ec1988b95e4a7fa7f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5dd1deb7173288babf011d27692886e32d1068d3dbb89e7d9754c6c73d84f90 0.600000000000 1686202 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": 1199581, "vin": [ { "gen": { "height": 1199571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5dd1deb7173288babf011d27692886e32d1068d3dbb89e7d9754c6c73d84f90" } } ], "extra": [ 1, 93, 49, 48, 192, 43, 94, 110, 255, 206, 216, 75, 20, 13, 117, 194, 64, 212, 246, 78, 148, 213, 187, 244, 46, 193, 152, 139, 149, 228, 167, 250, 127, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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