Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bf4836876a0c294d5e0fda6f8989d40a5b31e6d0dc62a082111462d287e1d0

Tx prefix hash: def1035b94a61176b07ef98e67ba3f87cd2ed107904195e9f0d64e4a0c73ee5e
Tx public key: 6b9e9d15f1a473da223ba2318dfa2f270dfb3536aabbac40baaa1a1c146e4962
Timestamp: 1715669110 Timestamp [UCT]: 2024-05-14 06:45:10 Age [y:d:h:m:s]: 00:286:23:28:54
Block: 1021654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205085 RingCT/type: yes/0
Extra: 016b9e9d15f1a473da223ba2318dfa2f270dfb3536aabbac40baaa1a1c146e49620211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf771aaab064d53ac4f03f1c573e849545126c6bfb97549f35b2d486d1f2cf07 0.600000000000 1486035 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": 1021664, "vin": [ { "gen": { "height": 1021654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf771aaab064d53ac4f03f1c573e849545126c6bfb97549f35b2d486d1f2cf07" } } ], "extra": [ 1, 107, 158, 157, 21, 241, 164, 115, 218, 34, 59, 162, 49, 141, 250, 47, 39, 13, 251, 53, 54, 170, 187, 172, 64, 186, 170, 26, 28, 20, 110, 73, 98, 2, 17, 0, 0, 0, 1, 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