Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a027179307f698956730fde5b9a8b704d0652ee1314a6ac0650ee39d794d4efb

Tx prefix hash: dd931dea8816936cb3e5f946b999caf0be4580adb510b50f20a2c19f5b21ba31
Tx public key: 2f986a9b4a01380306a338183b428be14e9be104c9e6373c9afad96c420c4a6a
Timestamp: 1721722187 Timestamp [UCT]: 2024-07-23 08:09:47 Age [y:d:h:m:s]: 00:185:17:06:40
Block: 1071822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132847 RingCT/type: yes/0
Extra: 012f986a9b4a01380306a338183b428be14e9be104c9e6373c9afad96c420c4a6a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27267ba18a17ee680ed0c0b946b8f836fb6324fd589b607ede2e5d00839c9192 0.600000000000 1544193 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": 1071832, "vin": [ { "gen": { "height": 1071822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27267ba18a17ee680ed0c0b946b8f836fb6324fd589b607ede2e5d00839c9192" } } ], "extra": [ 1, 47, 152, 106, 155, 74, 1, 56, 3, 6, 163, 56, 24, 59, 66, 139, 225, 78, 155, 225, 4, 201, 230, 55, 60, 154, 250, 217, 108, 66, 12, 74, 106, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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