Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330ffd6b86de384509af3cba7536723920f88346c3c9e2b686433cea77becde1

Tx prefix hash: d6b3eabab4229895702bbf77fd6096b0d5a4725e5a7e139e610fd8f7906f5240
Tx public key: ae1928bb1c35b0e8b6c538da4cab67997dad6d1d08dfb25ca4468296a6c9b8a3
Timestamp: 1753616907 Timestamp [UCT]: 2025-07-27 11:48:27 Age [y:d:h:m:s]: 00:069:12:52:59
Block: 1334486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48463 RingCT/type: yes/0
Extra: 01ae1928bb1c35b0e8b6c538da4cab67997dad6d1d08dfb25ca4468296a6c9b8a3021100000006ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f78dc70053a31819ecd5a830da4465de57b015522cb7e44d324060634d4ca00b 0.600000000000 1822287 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": 1334496, "vin": [ { "gen": { "height": 1334486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f78dc70053a31819ecd5a830da4465de57b015522cb7e44d324060634d4ca00b" } } ], "extra": [ 1, 174, 25, 40, 187, 28, 53, 176, 232, 182, 197, 56, 218, 76, 171, 103, 153, 125, 173, 109, 29, 8, 223, 178, 92, 164, 70, 130, 150, 166, 201, 184, 163, 2, 17, 0, 0, 0, 6, 239, 34, 20, 133, 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