Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76b55ebbc075ebab9a3cf52850c2940ceb1d3c30a73d233050f3adc47a2a9da

Tx prefix hash: de48a1eacfef271f807d3e00956140deb8856f674ee14250eb716f350af3b677
Tx public key: 713874c54a50b3240e47ce87cfb537b6b979f3a2af2a1b9ba1830c3e09a121d1
Timestamp: 1750492719 Timestamp [UCT]: 2025-06-21 07:58:39 Age [y:d:h:m:s]: 00:223:01:05:46
Block: 1309613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157191 RingCT/type: yes/0
Extra: 01713874c54a50b3240e47ce87cfb537b6b979f3a2af2a1b9ba1830c3e09a121d1021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: decbfac07bf98ba5b6588feb9df8c69e02a0eddf6e7eab98985d8e4c5964ccfd 0.600000000000 1797230 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": 1309623, "vin": [ { "gen": { "height": 1309613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "decbfac07bf98ba5b6588feb9df8c69e02a0eddf6e7eab98985d8e4c5964ccfd" } } ], "extra": [ 1, 113, 56, 116, 197, 74, 80, 179, 36, 14, 71, 206, 135, 207, 181, 55, 182, 185, 121, 243, 162, 175, 42, 27, 155, 161, 131, 12, 62, 9, 161, 33, 209, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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