Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe12e72de4534e8040797895752a16f1c94486dddbe14161ff92e5db26ed711

Tx prefix hash: 76668ba23dceda357c8add3cbf7d2e19ba4a696382b1cac406f7991e4462d9e3
Tx public key: 82e49a8dff2cbcc0d2c55f9773706f1dd635fe9b5b3152c5605f59ea1a3b5e2b
Timestamp: 1736533425 Timestamp [UCT]: 2025-01-10 18:23:45 Age [y:d:h:m:s]: 00:087:09:07:54
Block: 1194485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62220 RingCT/type: yes/0
Extra: 0182e49a8dff2cbcc0d2c55f9773706f1dd635fe9b5b3152c5605f59ea1a3b5e2b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68158d3241db5ce5d0e19b48abd59097dc19e4ef9da437515e353632afcca103 0.600000000000 1681056 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": 1194495, "vin": [ { "gen": { "height": 1194485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68158d3241db5ce5d0e19b48abd59097dc19e4ef9da437515e353632afcca103" } } ], "extra": [ 1, 130, 228, 154, 141, 255, 44, 188, 192, 210, 197, 95, 151, 115, 112, 111, 29, 214, 53, 254, 155, 91, 49, 82, 197, 96, 95, 89, 234, 26, 59, 94, 43, 2, 17, 0, 0, 0, 1, 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