Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1750588395340ddaa11ceca810f3d0f39a37be4e435fe8d853ec6148f8fb4c

Tx prefix hash: 141cb6876db6153fdcd177bee5ee889523347db1f510ba6b659bcc3b445a78a4
Tx public key: 28634b310086ccd3746f5e352847c86f4e30818fc047d05f17ae0a93a0f962b1
Timestamp: 1713279439 Timestamp [UCT]: 2024-04-16 14:57:19 Age [y:d:h:m:s]: 00:356:05:00:26
Block: 1001821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254658 RingCT/type: yes/0
Extra: 0128634b310086ccd3746f5e352847c86f4e30818fc047d05f17ae0a93a0f962b10211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 076af14241d6755d0990cc96fd87302b0ffc2ae1acfb9b1229a227ca17b787ad 0.600000000000 1462333 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": 1001831, "vin": [ { "gen": { "height": 1001821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "076af14241d6755d0990cc96fd87302b0ffc2ae1acfb9b1229a227ca17b787ad" } } ], "extra": [ 1, 40, 99, 75, 49, 0, 134, 204, 211, 116, 111, 94, 53, 40, 71, 200, 111, 78, 48, 129, 143, 192, 71, 208, 95, 23, 174, 10, 147, 160, 249, 98, 177, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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