Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17fb17f76b1f83c424c77753302862ca3351ec91d30619e4e86ea5d83edd67c9

Tx prefix hash: 78636f6beb6df15d1dc778daa6f8d75e71d10dba27b5a3ac6b606c088fadfcd6
Tx public key: 0248f5aa9e2db3eeba9673bea170f0552e0da3336947d5dcd28987886a6d34a2
Timestamp: 1754049415 Timestamp [UCT]: 2025-08-01 11:56:55 Age [y:d:h:m:s]: 00:179:12:09:05
Block: 1338018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127072 RingCT/type: yes/0
Extra: 010248f5aa9e2db3eeba9673bea170f0552e0da3336947d5dcd28987886a6d34a2021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e3355366a891904019e633df43cd93be634b8c769b7a0e0e776d173f4347033 0.600000000000 1825825 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": 1338028, "vin": [ { "gen": { "height": 1338018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e3355366a891904019e633df43cd93be634b8c769b7a0e0e776d173f4347033" } } ], "extra": [ 1, 2, 72, 245, 170, 158, 45, 179, 238, 186, 150, 115, 190, 161, 112, 240, 85, 46, 13, 163, 51, 105, 71, 213, 220, 210, 137, 135, 136, 106, 109, 52, 162, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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