Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eecfb4bca0fd59b107a3c70a86a578953dd87a56f12dbaed77d74e11f773bf41

Tx prefix hash: bd41017b1bfbb258ef25fcb1c896c4185108ce02e45b39e380b5e50c6cabf913
Tx public key: a77cdcc37e914c4592314f557a3a6d565f4ce3196b6bacabe95b3d8d471c9696
Timestamp: 1740988833 Timestamp [UCT]: 2025-03-03 08:00:33 Age [y:d:h:m:s]: 00:254:11:05:32
Block: 1231106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179603 RingCT/type: yes/0
Extra: 01a77cdcc37e914c4592314f557a3a6d565f4ce3196b6bacabe95b3d8d471c969602110000001a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94ca6681a664b6835996ca18dfe506fb334873ca4a89d08f73a1e0a0ce9d5cb 0.600000000000 1718011 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": 1231116, "vin": [ { "gen": { "height": 1231106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94ca6681a664b6835996ca18dfe506fb334873ca4a89d08f73a1e0a0ce9d5cb" } } ], "extra": [ 1, 167, 124, 220, 195, 126, 145, 76, 69, 146, 49, 79, 85, 122, 58, 109, 86, 95, 76, 227, 25, 107, 107, 172, 171, 233, 91, 61, 141, 71, 28, 150, 150, 2, 17, 0, 0, 0, 26, 31, 10, 83, 235, 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