Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c4f349b8c5d07211c0429a29bfebb017d1020589d3262e65c1617952dbb6d85

Tx prefix hash: 7316e26788ba6acd0e49267871a2d29da29b94b9100d4ae2a5aabdd77641c071
Tx public key: 739532c8b82861c2da3c7c93f4cbf37627e9a000b2ced43dc55947fd43ef337d
Timestamp: 1704674898 Timestamp [UCT]: 2024-01-08 00:48:18 Age [y:d:h:m:s]: 01:070:06:33:00
Block: 930478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311339 RingCT/type: yes/0
Extra: 01739532c8b82861c2da3c7c93f4cbf37627e9a000b2ced43dc55947fd43ef337d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cdc01b3f248951d7da4f9e74081582ca5fed07ee3dca1e96c1af7409da66bf4 0.600000000000 1388360 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": 930488, "vin": [ { "gen": { "height": 930478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cdc01b3f248951d7da4f9e74081582ca5fed07ee3dca1e96c1af7409da66bf4" } } ], "extra": [ 1, 115, 149, 50, 200, 184, 40, 97, 194, 218, 60, 124, 147, 244, 203, 243, 118, 39, 233, 160, 0, 178, 206, 212, 61, 197, 89, 71, 253, 67, 239, 51, 125, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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