Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e768924184d9f6881e44e81e405b8765a2c8e0b962b4b13d6878cea6e8d8abb9

Tx prefix hash: b15b16df914af0e77d9c50ef8f379fda78af9f4710a2cb1ba0e842b0de5a59a3
Tx public key: 5eb96d12b7b27b8b5f3047feb67e697886621343d4b0e7c9fdadb0d38d431782
Timestamp: 1736618753 Timestamp [UCT]: 2025-01-11 18:05:53 Age [y:d:h:m:s]: 00:067:07:39:48
Block: 1195191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47907 RingCT/type: yes/0
Extra: 015eb96d12b7b27b8b5f3047feb67e697886621343d4b0e7c9fdadb0d38d4317820211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b536969af36e7ade0eb6f95271e47311e008f1c6bd447e4c414fefd1ecb24d67 0.600000000000 1681780 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": 1195201, "vin": [ { "gen": { "height": 1195191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b536969af36e7ade0eb6f95271e47311e008f1c6bd447e4c414fefd1ecb24d67" } } ], "extra": [ 1, 94, 185, 109, 18, 183, 178, 123, 139, 95, 48, 71, 254, 182, 126, 105, 120, 134, 98, 19, 67, 212, 176, 231, 201, 253, 173, 176, 211, 141, 67, 23, 130, 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