Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43b36f7f55a1b4b5169f08db61bffcca3835fef4910ac0653d7be381231b70ac

Tx prefix hash: a3deb55e8e04d9fda2eb58ace7828cbc09387fe2f6e38e64420fb1f5d29c036f
Tx public key: 1a96b339eb73ab7f91906899eb4d6bed8bf9ae1546b1a6596d79d72ff1fa13f0
Timestamp: 1710281403 Timestamp [UCT]: 2024-03-12 22:10:03 Age [y:d:h:m:s]: 01:023:04:30:42
Block: 976995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277545 RingCT/type: yes/0
Extra: 011a96b339eb73ab7f91906899eb4d6bed8bf9ae1546b1a6596d79d72ff1fa13f00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cc3c9f9f510badfaf8daa983ed85f89b2bfdcdeabeae13e3325bf10bf3c5601 0.600000000000 1436996 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": 977005, "vin": [ { "gen": { "height": 976995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cc3c9f9f510badfaf8daa983ed85f89b2bfdcdeabeae13e3325bf10bf3c5601" } } ], "extra": [ 1, 26, 150, 179, 57, 235, 115, 171, 127, 145, 144, 104, 153, 235, 77, 107, 237, 139, 249, 174, 21, 70, 177, 166, 89, 109, 121, 215, 47, 241, 250, 19, 240, 2, 17, 0, 0, 0, 4, 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