Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddf192da00fd27ef41920f54e75e43d6530128cb538dcb2092de3b60e86fc334

Tx prefix hash: 413bb44a70b1269ee021173df7dea1a41185536ac0d3cf1f8f401028c30b2026
Tx public key: e7df0b25ec37f3aad96e60e7e6dbe374d11eba23049c13eec79839aa5174bf85
Timestamp: 1736838054 Timestamp [UCT]: 2025-01-14 07:00:54 Age [y:d:h:m:s]: 00:154:11:26:21
Block: 1197004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110111 RingCT/type: yes/0
Extra: 01e7df0b25ec37f3aad96e60e7e6dbe374d11eba23049c13eec79839aa5174bf850211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2c25ea6e17258efc714185eae1eb8d547cae1b4b9ae0a5cd8089e8f4033a056 0.600000000000 1683609 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": 1197014, "vin": [ { "gen": { "height": 1197004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2c25ea6e17258efc714185eae1eb8d547cae1b4b9ae0a5cd8089e8f4033a056" } } ], "extra": [ 1, 231, 223, 11, 37, 236, 55, 243, 170, 217, 110, 96, 231, 230, 219, 227, 116, 209, 30, 186, 35, 4, 156, 19, 238, 199, 152, 57, 170, 81, 116, 191, 133, 2, 17, 0, 0, 0, 2, 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