Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb27efa0e6e10d4f781bdd80c653295e1a1c31a0bddb88f9a3be813e0b7a9e5

Tx prefix hash: c50e2a0e7117614477eddc2297b775e73fa97c89a46e1b263c45ff34345764fc
Tx public key: 0e090274db7393f517b1328bad1c900b1d687ea674feae6740015991e613318c
Timestamp: 1750200708 Timestamp [UCT]: 2025-06-17 22:51:48 Age [y:d:h:m:s]: 00:189:05:01:21
Block: 1307244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133072 RingCT/type: yes/0
Extra: 010e090274db7393f517b1328bad1c900b1d687ea674feae6740015991e613318c021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed9a5474f75481eab53882da07df8d4303d4cba7a9c8d0c0df496119eff9e595 0.600000000000 1794855 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": 1307254, "vin": [ { "gen": { "height": 1307244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed9a5474f75481eab53882da07df8d4303d4cba7a9c8d0c0df496119eff9e595" } } ], "extra": [ 1, 14, 9, 2, 116, 219, 115, 147, 245, 23, 177, 50, 139, 173, 28, 144, 11, 29, 104, 126, 166, 116, 254, 174, 103, 64, 1, 89, 145, 230, 19, 49, 140, 2, 17, 0, 0, 0, 6, 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