Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4083e91f8eb18daeedc7126e946c7a5d85cc2031dde7c179d37e77ee0b75377

Tx prefix hash: c70cdd8278c51c7ca9182befd33b6a5f7ce2b58e2dfb56676d57bfa2a4efebfd
Tx public key: 8eff42ee5a24defc1c4648a4eae38c913f32b566ed91ad900994e74d04eb9b70
Timestamp: 1719847255 Timestamp [UCT]: 2024-07-01 15:20:55 Age [y:d:h:m:s]: 00:291:19:33:46
Block: 1056287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208510 RingCT/type: yes/0
Extra: 018eff42ee5a24defc1c4648a4eae38c913f32b566ed91ad900994e74d04eb9b70021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53a35cb3582adc793de8c19cc7aee5a3984f43b03ef4f435c7664e10aec75360 0.600000000000 1526700 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": 1056297, "vin": [ { "gen": { "height": 1056287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53a35cb3582adc793de8c19cc7aee5a3984f43b03ef4f435c7664e10aec75360" } } ], "extra": [ 1, 142, 255, 66, 238, 90, 36, 222, 252, 28, 70, 72, 164, 234, 227, 140, 145, 63, 50, 181, 102, 237, 145, 173, 144, 9, 148, 231, 77, 4, 235, 155, 112, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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