Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9547407ae96066aea73cc911d4acecf94e5f203e89dc183f1b4b680d84d700e

Tx prefix hash: 3f37ee6965870633d10bae60fad224b639efdb50d3536e4ef6ad172107241136
Tx public key: 39699b3a8e5bb6c583509aa94b0822f36fe0366197e4b8fd2eb1589e80452d76
Timestamp: 1737710985 Timestamp [UCT]: 2025-01-24 09:29:45 Age [y:d:h:m:s]: 00:144:16:33:32
Block: 1204192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103149 RingCT/type: yes/0
Extra: 0139699b3a8e5bb6c583509aa94b0822f36fe0366197e4b8fd2eb1589e80452d760211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f36c0ec507f783e24152d0d54ae3c9b0c363ca69b88f226d6e5002d6b65dd6b 0.600000000000 1690877 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": 1204202, "vin": [ { "gen": { "height": 1204192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f36c0ec507f783e24152d0d54ae3c9b0c363ca69b88f226d6e5002d6b65dd6b" } } ], "extra": [ 1, 57, 105, 155, 58, 142, 91, 182, 197, 131, 80, 154, 169, 75, 8, 34, 243, 111, 224, 54, 97, 151, 228, 184, 253, 46, 177, 88, 158, 128, 69, 45, 118, 2, 17, 0, 0, 0, 8, 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