Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2e96a989af62e416f32420b8f15d288fe1667b8789f4b861b281b7aac80809

Tx prefix hash: 53f4bf7613926cb00b888d3f81d8db2b015eb3645ab3bdeb49063e7c3135b4bf
Tx public key: 217d4e022d99f40a7d4ae8316a636efde0eb9d532b45dbd6dbd0944c2d349abd
Timestamp: 1743537543 Timestamp [UCT]: 2025-04-01 19:59:03 Age [y:d:h:m:s]: 00:222:23:46:39
Block: 1252187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157111 RingCT/type: yes/0
Extra: 01217d4e022d99f40a7d4ae8316a636efde0eb9d532b45dbd6dbd0944c2d349abd0211000000014060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8a812c25a557fd881b41896fe116a4d13e54e0a609d69847522282820005498 0.600000000000 1739266 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": 1252197, "vin": [ { "gen": { "height": 1252187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8a812c25a557fd881b41896fe116a4d13e54e0a609d69847522282820005498" } } ], "extra": [ 1, 33, 125, 78, 2, 45, 153, 244, 10, 125, 74, 232, 49, 106, 99, 110, 253, 224, 235, 157, 83, 43, 69, 219, 214, 219, 208, 148, 76, 45, 52, 154, 189, 2, 17, 0, 0, 0, 1, 64, 96, 246, 210, 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