Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa0347cffb52897e30ee4eb9cc5300c67e722d9bb093a1028c71ab3655d8f55

Tx prefix hash: 743551094156d511c577c2c0f7eaa0f6240106de239cf8ab8225842cbc8e427e
Tx public key: 2501e5981d6ab1fcf68bc0602368f5b1034fdfca1b2fedc3bbf574ff4fd86e91
Timestamp: 1717488383 Timestamp [UCT]: 2024-06-04 08:06:23 Age [y:d:h:m:s]: 00:309:16:52:38
Block: 1036745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221323 RingCT/type: yes/0
Extra: 012501e5981d6ab1fcf68bc0602368f5b1034fdfca1b2fedc3bbf574ff4fd86e910211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4a744eb4ec79e5026c346629d05a1de7d4c7f2543917da0d079e00e61a2c76 0.600000000000 1505274 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": 1036755, "vin": [ { "gen": { "height": 1036745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4a744eb4ec79e5026c346629d05a1de7d4c7f2543917da0d079e00e61a2c76" } } ], "extra": [ 1, 37, 1, 229, 152, 29, 106, 177, 252, 246, 139, 192, 96, 35, 104, 245, 177, 3, 79, 223, 202, 27, 47, 237, 195, 187, 245, 116, 255, 79, 216, 110, 145, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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