Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5be95e4174701dac97c0aab5e1434aae5d17b882ee968d0a180a67c6dffbe1

Tx prefix hash: 54424dd5ef51fe806dc251e6b7efd3bab7ee3bc05f810b5a3bbbf164ceda420c
Tx public key: ab12760f54e1ac9cdea83093f853892fe496275ca60f3ca2d38ef9fab8d009e4
Timestamp: 1740991491 Timestamp [UCT]: 2025-03-03 08:44:51 Age [y:d:h:m:s]: 00:259:13:23:17
Block: 1231122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183253 RingCT/type: yes/0
Extra: 01ab12760f54e1ac9cdea83093f853892fe496275ca60f3ca2d38ef9fab8d009e40211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed378aea21ef5bdd90cbe4f680d2fcfda70c220d625075dd11faedeaa74cf2f6 0.600000000000 1718027 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": 1231132, "vin": [ { "gen": { "height": 1231122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed378aea21ef5bdd90cbe4f680d2fcfda70c220d625075dd11faedeaa74cf2f6" } } ], "extra": [ 1, 171, 18, 118, 15, 84, 225, 172, 156, 222, 168, 48, 147, 248, 83, 137, 47, 228, 150, 39, 92, 166, 15, 60, 162, 211, 142, 249, 250, 184, 208, 9, 228, 2, 17, 0, 0, 0, 5, 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