Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916f8b1cbf398919c888e2632e2c7a1bc306367af939461ce97944572bcf5110

Tx prefix hash: b5ced60dd2d623409cfddab9893e32a87927a0561a31965bfdc1b617885a7c67
Tx public key: c0d8a0d695337d316caa37f1ac6a7a3887f767952182aaa41b7097c238b38ea2
Timestamp: 1749570441 Timestamp [UCT]: 2025-06-10 15:47:21 Age [y:d:h:m:s]: 00:151:13:50:11
Block: 1302160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106000 RingCT/type: yes/0
Extra: 01c0d8a0d695337d316caa37f1ac6a7a3887f767952182aaa41b7097c238b38ea20211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507fe138f38ae8e8c1dd72fd9d727df54623ecdf91f209a627f1fff9dd92f9b3 0.600000000000 1789729 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": 1302170, "vin": [ { "gen": { "height": 1302160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507fe138f38ae8e8c1dd72fd9d727df54623ecdf91f209a627f1fff9dd92f9b3" } } ], "extra": [ 1, 192, 216, 160, 214, 149, 51, 125, 49, 108, 170, 55, 241, 172, 106, 122, 56, 135, 247, 103, 149, 33, 130, 170, 164, 27, 112, 151, 194, 56, 179, 142, 162, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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