Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a652c5fdb1f4801427a1bf85f73131e973102463db76a1c4744663fbc331d7

Tx prefix hash: 8f1cc3c7ff690af400a3117ebc3007bac872a4ae83e26c658fe99b02c216d4c4
Tx public key: b8e05c265d2343ef66c36f743f37e45e863918e0bf091591a8c84fcac3c72128
Timestamp: 1582641706 Timestamp [UCT]: 2020-02-25 14:41:46 Age [y:d:h:m:s]: 05:061:12:23:38
Block: 72216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197359 RingCT/type: yes/0
Extra: 01b8e05c265d2343ef66c36f743f37e45e863918e0bf091591a8c84fcac3c7212802110000000256c366d3000000000000000000

1 output(s) for total of 353.768543976000 dcy

stealth address amount amount idx
00: b3cc803698a5a4d7397f2e5cb4cd0f82eb0681eeb6475107584330d307011816 353.768543976000 133382 of 0

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": 72226, "vin": [ { "gen": { "height": 72216 } } ], "vout": [ { "amount": 353768543976, "target": { "key": "b3cc803698a5a4d7397f2e5cb4cd0f82eb0681eeb6475107584330d307011816" } } ], "extra": [ 1, 184, 224, 92, 38, 93, 35, 67, 239, 102, 195, 111, 116, 63, 55, 228, 94, 134, 57, 24, 224, 191, 9, 21, 145, 168, 200, 79, 202, 195, 199, 33, 40, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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