Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b60c4cf430b33405fc1b4cd4412357990f410989ccf11964bfc02e894740f872

Tx prefix hash: f6c18ad052ae4e6648007ccf88b3db3c6fd9a158300138f51583b536e82da0b9
Tx public key: f3176bbc6e8a22d68250b69ff828ac828b3c79f7acce5d08b4b18c9c48aa97d9
Timestamp: 1757274189 Timestamp [UCT]: 2025-09-07 19:43:09 Age [y:d:h:m:s]: 00:081:11:34:06
Block: 1363566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58246 RingCT/type: yes/0
Extra: 01f3176bbc6e8a22d68250b69ff828ac828b3c79f7acce5d08b4b18c9c48aa97d9021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21b625b1ef4c71ed43cd7fcae134384be60b4e61928d731c03da45f2fb21041b 0.600000000000 1851605 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": 1363576, "vin": [ { "gen": { "height": 1363566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21b625b1ef4c71ed43cd7fcae134384be60b4e61928d731c03da45f2fb21041b" } } ], "extra": [ 1, 243, 23, 107, 188, 110, 138, 34, 214, 130, 80, 182, 159, 248, 40, 172, 130, 139, 60, 121, 247, 172, 206, 93, 8, 180, 177, 140, 156, 72, 170, 151, 217, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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