Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7bda9a18e7aa043ffcabecf5e2fedb50a53c661b9ab8050788f80b1a8468235

Tx prefix hash: 1953f5b052e067126841527749811d5a5cf394c2c0f6714ab1caca8480b95b10
Tx public key: 83de04ceb690d4d83b71fb25e5ecac07a473c4118fb8bd890ae0dccbc78e1a05
Timestamp: 1738888911 Timestamp [UCT]: 2025-02-07 00:41:51 Age [y:d:h:m:s]: 00:244:12:05:56
Block: 1213726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172444 RingCT/type: yes/0
Extra: 0183de04ceb690d4d83b71fb25e5ecac07a473c4118fb8bd890ae0dccbc78e1a05021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 610beb75a3e02d74d67f9840afa26eb5efe5e4e512a6e8639cca4303d82df117 0.600000000000 1700507 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": 1213736, "vin": [ { "gen": { "height": 1213726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "610beb75a3e02d74d67f9840afa26eb5efe5e4e512a6e8639cca4303d82df117" } } ], "extra": [ 1, 131, 222, 4, 206, 182, 144, 212, 216, 59, 113, 251, 37, 229, 236, 172, 7, 164, 115, 196, 17, 143, 184, 189, 137, 10, 224, 220, 203, 199, 142, 26, 5, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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