Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0cf9e6a4f9648fdcea8438164e54072fcc016b7f56a5896dcd004464d726b12

Tx prefix hash: d34ea6ff7951b0404c07a10c4ca1f0d9de545b7457dfa77972e376a7a438c23e
Tx public key: 031588c58e1d114308017ee0656459406d5a85784a084a1cb668dc1c00ce8667
Timestamp: 1710856798 Timestamp [UCT]: 2024-03-19 13:59:58 Age [y:d:h:m:s]: 01:043:08:09:36
Block: 981768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291954 RingCT/type: yes/0
Extra: 01031588c58e1d114308017ee0656459406d5a85784a084a1cb668dc1c00ce866702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c475d154a898fdffa3b1d1dc18d7f93d25970cf40b008fef7d16e5b9c98e9a 0.600000000000 1441867 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": 981778, "vin": [ { "gen": { "height": 981768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c475d154a898fdffa3b1d1dc18d7f93d25970cf40b008fef7d16e5b9c98e9a" } } ], "extra": [ 1, 3, 21, 136, 197, 142, 29, 17, 67, 8, 1, 126, 224, 101, 100, 89, 64, 109, 90, 133, 120, 74, 8, 74, 28, 182, 104, 220, 28, 0, 206, 134, 103, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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