Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba19dcaf7cd4e6ccec292a91616768ca2f4033dd6c9937b2672deb545d42f0d4

Tx prefix hash: 7ec0d2f416f26bdc96c7ae8b4704fee0316aac1d7f0448b5f23682f8fff7b51c
Tx public key: 077b222956b9cb138a1bdc41bcdab9d233045e9b5bdbb19addc74b2462401dbd
Timestamp: 1646849310 Timestamp [UCT]: 2022-03-09 18:08:30 Age [y:d:h:m:s]: 03:038:17:40:53
Block: 454848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807841 RingCT/type: yes/0
Extra: 01077b222956b9cb138a1bdc41bcdab9d233045e9b5bdbb19addc74b2462401dbd02110000002cd3fcec30000000000000000000

1 output(s) for total of 19.094136867000 dcy

stealth address amount amount idx
00: e7042c56a9203692c610c4f567f0d283a8f71625225e6b22616ae56bbd078025 19.094136867000 870577 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": 454858, "vin": [ { "gen": { "height": 454848 } } ], "vout": [ { "amount": 19094136867, "target": { "key": "e7042c56a9203692c610c4f567f0d283a8f71625225e6b22616ae56bbd078025" } } ], "extra": [ 1, 7, 123, 34, 41, 86, 185, 203, 19, 138, 27, 220, 65, 188, 218, 185, 210, 51, 4, 94, 155, 91, 219, 177, 154, 221, 199, 75, 36, 98, 64, 29, 189, 2, 17, 0, 0, 0, 44, 211, 252, 236, 48, 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