Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202b3d29b1d7d7269a85a0918371cd0d7e19ca4be6a79e1f594b4ddd9075185b

Tx prefix hash: 0d58e11c1b17164d4bebcb49d7b11a28d8dcbf3987695dc6f03b2804c78fb1c1
Tx public key: 3ce4d67c108fcefe98b1ef78339b5f92e0f9ff2fb49d13487371943542cd4080
Timestamp: 1743954860 Timestamp [UCT]: 2025-04-06 15:54:20 Age [y:d:h:m:s]: 00:216:10:55:23
Block: 1255644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152428 RingCT/type: yes/0
Extra: 013ce4d67c108fcefe98b1ef78339b5f92e0f9ff2fb49d13487371943542cd40800211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd514f2b76b4fbed0a2902d8d67d8f19c84c39cf5fe05e71114da0b6008d113a 0.600000000000 1742749 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": 1255654, "vin": [ { "gen": { "height": 1255644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd514f2b76b4fbed0a2902d8d67d8f19c84c39cf5fe05e71114da0b6008d113a" } } ], "extra": [ 1, 60, 228, 214, 124, 16, 143, 206, 254, 152, 177, 239, 120, 51, 155, 95, 146, 224, 249, 255, 47, 180, 157, 19, 72, 115, 113, 148, 53, 66, 205, 64, 128, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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