Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fee8f0d97ab37779125925db73ddfd1b8ce3cbf026965b9a12182dd9296dd6

Tx prefix hash: 7dc363994f5fbc329f92cbcdcd0a38f160a266d9a6118b4eac90143773bed9aa
Tx public key: c658c7ec84dc58e8f8bff30340f3770e8e45eca9e5cc8ad44f2d2a4f8757e4d8
Timestamp: 1721228847 Timestamp [UCT]: 2024-07-17 15:07:27 Age [y:d:h:m:s]: 00:176:18:07:29
Block: 1067758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126458 RingCT/type: yes/0
Extra: 01c658c7ec84dc58e8f8bff30340f3770e8e45eca9e5cc8ad44f2d2a4f8757e4d802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1385f1eaa5d19d15de49d720a22fcc9d9ae2213545c8a28dcef1d046c7c628c 0.600000000000 1538657 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": 1067768, "vin": [ { "gen": { "height": 1067758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1385f1eaa5d19d15de49d720a22fcc9d9ae2213545c8a28dcef1d046c7c628c" } } ], "extra": [ 1, 198, 88, 199, 236, 132, 220, 88, 232, 248, 191, 243, 3, 64, 243, 119, 14, 142, 69, 236, 169, 229, 204, 138, 212, 79, 45, 42, 79, 135, 87, 228, 216, 2, 17, 0, 0, 0, 1, 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