Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6671b8402233c0c5700cd8025d301a70171d43dd822f4a445dd8e0deb6aadeb7

Tx prefix hash: 7de1cc942a5a516ab326e8d458ef31b3d21364650018fb524a9bdca4c23cf4db
Tx public key: 547ffc6940213bd84f248564dc4562fb74b0b9c5ae100a1418812b5facc73fa2
Timestamp: 1635602367 Timestamp [UCT]: 2021-10-30 13:59:27 Age [y:d:h:m:s]: 03:179:09:48:16
Block: 363677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 906521 RingCT/type: yes/0
Extra: 01547ffc6940213bd84f248564dc4562fb74b0b9c5ae100a1418812b5facc73fa20211000000064a0f5013000000000000000000

1 output(s) for total of 38.281375403000 dcy

stealth address amount amount idx
00: ed37b4f3d1a07defb4baf2919e782d0a640200d7be8394b15cdb0345838b3bc7 38.281375403000 739081 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": 363687, "vin": [ { "gen": { "height": 363677 } } ], "vout": [ { "amount": 38281375403, "target": { "key": "ed37b4f3d1a07defb4baf2919e782d0a640200d7be8394b15cdb0345838b3bc7" } } ], "extra": [ 1, 84, 127, 252, 105, 64, 33, 59, 216, 79, 36, 133, 100, 220, 69, 98, 251, 116, 176, 185, 197, 174, 16, 10, 20, 24, 129, 43, 95, 172, 199, 63, 162, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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