Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd49d0d57716122a2ce9b3288be13a6d943e6bed49a5b22ddad3b4321d0a9172

Tx prefix hash: 580983d9d93dc399c31065fcc0a79b48de554e80b0b3b862ce4b1030c404a685
Tx public key: 6de0a0dc8d56436cac7dcfc63894790e95a60bbf449b48521a0eac15b580ed84
Timestamp: 1710873174 Timestamp [UCT]: 2024-03-19 18:32:54 Age [y:d:h:m:s]: 01:277:14:26:54
Block: 981911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457128 RingCT/type: yes/0
Extra: 016de0a0dc8d56436cac7dcfc63894790e95a60bbf449b48521a0eac15b580ed84021100000003a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fbd0223bba0a175dfc3cad26b5ae006de9ff174ea06f546c23692ec07c1842a 0.600000000000 1442014 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": 981921, "vin": [ { "gen": { "height": 981911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fbd0223bba0a175dfc3cad26b5ae006de9ff174ea06f546c23692ec07c1842a" } } ], "extra": [ 1, 109, 224, 160, 220, 141, 86, 67, 108, 172, 125, 207, 198, 56, 148, 121, 14, 149, 166, 11, 191, 68, 155, 72, 82, 26, 14, 172, 21, 181, 128, 237, 132, 2, 17, 0, 0, 0, 3, 165, 223, 157, 134, 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