Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ea103e2a77498032162f2f660a20e87019c857a64919ca323a32b81f555613

Tx prefix hash: b730af3fb5a8c5309e53c1328b6a0602aaee27fa28918432c5190df534e50c6e
Tx public key: 1650dc3025a0fa8526d319b218cb86160b8c251dd03a7f276b4df313f13884b2
Timestamp: 1763575311 Timestamp [UCT]: 2025-11-19 18:01:51 Age [y:d:h:m:s]: 00:034:04:20:20
Block: 1415697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24458 RingCT/type: yes/0
Extra: 011650dc3025a0fa8526d319b218cb86160b8c251dd03a7f276b4df313f13884b202110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35390c67d8e6ab5ffded956142b9589f499fa756e298bf1449a67066d5aee580 0.600000000000 1904202 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": 1415707, "vin": [ { "gen": { "height": 1415697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35390c67d8e6ab5ffded956142b9589f499fa756e298bf1449a67066d5aee580" } } ], "extra": [ 1, 22, 80, 220, 48, 37, 160, 250, 133, 38, 211, 25, 178, 24, 203, 134, 22, 11, 140, 37, 29, 208, 58, 127, 39, 107, 77, 243, 19, 241, 56, 132, 178, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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