Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c45d97be7420f29b728b0bd82879b9a27cae558facc05649ebbfee8ec051e7f

Tx prefix hash: d30ab89a384f210b59fd58ab90e8f0ef15e60f7ed61e379a6323f88cb2fc6bf6
Tx public key: c345c22018b22f70d0046b1fdaf31cee6dbde6a88f085c46d9dceb9b68285de4
Timestamp: 1735162262 Timestamp [UCT]: 2024-12-25 21:31:02 Age [y:d:h:m:s]: 00:089:11:32:38
Block: 1183140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63723 RingCT/type: yes/0
Extra: 01c345c22018b22f70d0046b1fdaf31cee6dbde6a88f085c46d9dceb9b68285de4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37a33aefe9d67172523701b03776d49f585227bcca2798472bca5ce824e4a0b0 0.600000000000 1669581 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": 1183150, "vin": [ { "gen": { "height": 1183140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37a33aefe9d67172523701b03776d49f585227bcca2798472bca5ce824e4a0b0" } } ], "extra": [ 1, 195, 69, 194, 32, 24, 178, 47, 112, 208, 4, 107, 31, 218, 243, 28, 238, 109, 189, 230, 168, 143, 8, 92, 70, 217, 220, 235, 155, 104, 40, 93, 228, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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