Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d2992fade188aae1f0cb04e015fa92d929c9db9eb6738e55a89b076b7389af

Tx prefix hash: b972c073e797db6d880e114db2c39a2c7c3f6cb2aafc4adffce5f6f6d1b2cc17
Tx public key: 831f0cf9c9e934f3774390aed96ba89889797bd5c2ec7d3afe1c9ed29d972000
Timestamp: 1745464980 Timestamp [UCT]: 2025-04-24 03:23:00 Age [y:d:h:m:s]: 00:211:19:49:15
Block: 1268162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149106 RingCT/type: yes/0
Extra: 01831f0cf9c9e934f3774390aed96ba89889797bd5c2ec7d3afe1c9ed29d9720000211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58ed2f55d4ae68a3c4d22742d1f1f83869fa167f8f3f89bf262c2e9e782681dc 0.600000000000 1755391 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": 1268172, "vin": [ { "gen": { "height": 1268162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58ed2f55d4ae68a3c4d22742d1f1f83869fa167f8f3f89bf262c2e9e782681dc" } } ], "extra": [ 1, 131, 31, 12, 249, 201, 233, 52, 243, 119, 67, 144, 174, 217, 107, 168, 152, 137, 121, 123, 213, 194, 236, 125, 58, 254, 28, 158, 210, 157, 151, 32, 0, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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