Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbcd7eae6d73aaba54fb48316c628c9b3ed9400021400c242b04f9eb7fab6b18

Tx prefix hash: f8bc4a25cd40caedbc49af82b9936a50bec34953fa12e729df005f937fa1d106
Tx public key: 8c9f5e52d8bf34ec4325f8b5e6604c46e585af429d48b433d85f4e43b4b5e5c1
Timestamp: 1721590877 Timestamp [UCT]: 2024-07-21 19:41:17 Age [y:d:h:m:s]: 00:247:13:26:40
Block: 1070732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176844 RingCT/type: yes/0
Extra: 018c9f5e52d8bf34ec4325f8b5e6604c46e585af429d48b433d85f4e43b4b5e5c102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a65947e502dd1fb813cbf2d45f2ff4a265566512f1be35cdd2ccf2b0a11cbc75 0.600000000000 1542689 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": 1070742, "vin": [ { "gen": { "height": 1070732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a65947e502dd1fb813cbf2d45f2ff4a265566512f1be35cdd2ccf2b0a11cbc75" } } ], "extra": [ 1, 140, 159, 94, 82, 216, 191, 52, 236, 67, 37, 248, 181, 230, 96, 76, 70, 229, 133, 175, 66, 157, 72, 180, 51, 216, 95, 78, 67, 180, 181, 229, 193, 2, 17, 0, 0, 0, 9, 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