Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cf1b3b70af4eab0cee20bdffbc65cfd879aeca922898b228dff6f13527b4ed

Tx prefix hash: dff313e33a86d43364120a4f60e3ac702abfd115943107cfc86abe90c1391dd3
Tx public key: 0a722e0fadd04e1defae71d8a7c1342ff0c83b9a6543421816c7aa0b6bd0f219
Timestamp: 1743608392 Timestamp [UCT]: 2025-04-02 15:39:52 Age [y:d:h:m:s]: 00:041:23:19:02
Block: 1252789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30034 RingCT/type: yes/0
Extra: 010a722e0fadd04e1defae71d8a7c1342ff0c83b9a6543421816c7aa0b6bd0f2190211000000084060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f7f74010b90c55dc75112efeb9a2a56f0145c5334b1b63710b0980c43befc86 0.600000000000 1739870 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": 1252799, "vin": [ { "gen": { "height": 1252789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7f74010b90c55dc75112efeb9a2a56f0145c5334b1b63710b0980c43befc86" } } ], "extra": [ 1, 10, 114, 46, 15, 173, 208, 78, 29, 239, 174, 113, 216, 167, 193, 52, 47, 240, 200, 59, 154, 101, 67, 66, 24, 22, 199, 170, 11, 107, 208, 242, 25, 2, 17, 0, 0, 0, 8, 64, 96, 246, 210, 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