Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a143e6a7bfe1df55d2f011270b67ccbf60ab11546f198e065b58f0516139efcf

Tx prefix hash: 591093122f40dfa51bc6a16d6f77512144e1f0bab8d3ffad7a5c22dc4649ad06
Tx public key: 7407e5e9d5372cddf5e311178d46ecc0f7fa43aeb3fba3d66442f410c5a8c125
Timestamp: 1730341602 Timestamp [UCT]: 2024-10-31 02:26:42 Age [y:d:h:m:s]: 00:145:18:36:27
Block: 1143205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104022 RingCT/type: yes/0
Extra: 017407e5e9d5372cddf5e311178d46ecc0f7fa43aeb3fba3d66442f410c5a8c12502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ba7fa081ae0310f1d4b35c83e74e7fa19051ebc176b304ca609907c6770c674 0.600000000000 1627068 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": 1143215, "vin": [ { "gen": { "height": 1143205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ba7fa081ae0310f1d4b35c83e74e7fa19051ebc176b304ca609907c6770c674" } } ], "extra": [ 1, 116, 7, 229, 233, 213, 55, 44, 221, 245, 227, 17, 23, 141, 70, 236, 192, 247, 250, 67, 174, 179, 251, 163, 214, 100, 66, 244, 16, 197, 168, 193, 37, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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