Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489694bd0d4e70bb5a9cac4dc3dd25a031ea1048c4737b36207909582c6a157f

Tx prefix hash: 31ba9e57c14c8871a6407f2522d5d1157dd85627f471b2736dc1afb35227351d
Tx public key: 5f074473c79dde7119a0a8d7d8c470a00415d53c8b0818f7e533ce6371d68a48
Timestamp: 1763383759 Timestamp [UCT]: 2025-11-17 12:49:19 Age [y:d:h:m:s]: 00:004:11:12:33
Block: 1414102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3192 RingCT/type: yes/0
Extra: 015f074473c79dde7119a0a8d7d8c470a00415d53c8b0818f7e533ce6371d68a4802110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d7d690410dbc36ce95d49eea4ba1e4ed349daf8ede826e56f72e69856514ce 0.600000000000 1902589 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": 1414112, "vin": [ { "gen": { "height": 1414102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d7d690410dbc36ce95d49eea4ba1e4ed349daf8ede826e56f72e69856514ce" } } ], "extra": [ 1, 95, 7, 68, 115, 199, 157, 222, 113, 25, 160, 168, 215, 216, 196, 112, 160, 4, 21, 213, 60, 139, 8, 24, 247, 229, 51, 206, 99, 113, 214, 138, 72, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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