Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e260f8474b1c9af066ac658ce0c32254d2db4376cdf94f76249c1889887433

Tx prefix hash: 9852674ccd3d9c4ea2026a67a15f6bcfba193a0311e7f31ed652c4974a42c263
Tx public key: 4d84d4fd578edebb309432c3a4a48760bc8cd381874110df135b7dffd819ba0e
Timestamp: 1721477912 Timestamp [UCT]: 2024-07-20 12:18:32 Age [y:d:h:m:s]: 00:248:05:30:01
Block: 1069809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177321 RingCT/type: yes/0
Extra: 014d84d4fd578edebb309432c3a4a48760bc8cd381874110df135b7dffd819ba0e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5106ad9f078a7f935b19a598af3f54a5fa59e7dcc02dfca0b6f4e46c45121ee6 0.600000000000 1541386 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": 1069819, "vin": [ { "gen": { "height": 1069809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5106ad9f078a7f935b19a598af3f54a5fa59e7dcc02dfca0b6f4e46c45121ee6" } } ], "extra": [ 1, 77, 132, 212, 253, 87, 142, 222, 187, 48, 148, 50, 195, 164, 164, 135, 96, 188, 140, 211, 129, 135, 65, 16, 223, 19, 91, 125, 255, 216, 25, 186, 14, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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