Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7c85f286c9383560b29a4e55262e794535f05e9583e0f62ede8ed025e0572f

Tx prefix hash: d190d3970f14f940a358b0645c0fa58ad6d15d9e5d488f92d9fd8db95fc9e4fa
Tx public key: 29daeeaa14b45dc0e2864edfdcd983cd02ced12f53b1f3a2c1c1e2b86b9c7587
Timestamp: 1716601008 Timestamp [UCT]: 2024-05-25 01:36:48 Age [y:d:h:m:s]: 01:169:20:01:55
Block: 1029384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379967 RingCT/type: yes/0
Extra: 0129daeeaa14b45dc0e2864edfdcd983cd02ced12f53b1f3a2c1c1e2b86b9c758702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3cd7c0adafa4a54384a3810ebb6978ed43c0a265f550fdd5fdc2e0d1f3706f0 0.600000000000 1497459 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": 1029394, "vin": [ { "gen": { "height": 1029384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3cd7c0adafa4a54384a3810ebb6978ed43c0a265f550fdd5fdc2e0d1f3706f0" } } ], "extra": [ 1, 41, 218, 238, 170, 20, 180, 93, 192, 226, 134, 78, 223, 220, 217, 131, 205, 2, 206, 209, 47, 83, 177, 243, 162, 193, 193, 226, 184, 107, 156, 117, 135, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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