Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696445c464056465d2dff4327dca16697c305c52a5d46449978d660de67fd7d9

Tx prefix hash: fd98b03c91d90f5b13b69d77f50dcbda9e850e0b379ef5ca7102e9ce4650142c
Tx public key: 1bc2c4e3148782bbcd969855739494dd8dc1bcfbbaeee872fa2e5a76e54b3fb5
Timestamp: 1740264201 Timestamp [UCT]: 2025-02-22 22:43:21 Age [y:d:h:m:s]: 00:227:21:14:47
Block: 1225089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160576 RingCT/type: yes/0
Extra: 011bc2c4e3148782bbcd969855739494dd8dc1bcfbbaeee872fa2e5a76e54b3fb50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7db4a5d16e30842f0e9118d4536cac8f9d6aaa7eb7f558906c9056dd3bea8b8e 0.600000000000 1711954 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": 1225099, "vin": [ { "gen": { "height": 1225089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7db4a5d16e30842f0e9118d4536cac8f9d6aaa7eb7f558906c9056dd3bea8b8e" } } ], "extra": [ 1, 27, 194, 196, 227, 20, 135, 130, 187, 205, 150, 152, 85, 115, 148, 148, 221, 141, 193, 188, 251, 186, 238, 232, 114, 250, 46, 90, 118, 229, 75, 63, 181, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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