Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5df0cac42b5f41fdd81f16e3d3d6b912c20d51a200eabb3bd0a231000bf1b7

Tx prefix hash: 485c61d7dead5c522191bb3261b9a9d71484550e7de95197065cf424c6cd6606
Tx public key: cf4ff339a955a34162cd8da0a85e4e5fa142b9bb62831300401a439ac3c99d5d
Timestamp: 1703153326 Timestamp [UCT]: 2023-12-21 10:08:46 Age [y:d:h:m:s]: 01:025:12:18:44
Block: 917887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279579 RingCT/type: yes/0
Extra: 01cf4ff339a955a34162cd8da0a85e4e5fa142b9bb62831300401a439ac3c99d5d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81af0dc7e1182e1650b87fbc2d45dbdd56e0222abdff6333632a0215d0ae8eaa 0.600000000000 1375511 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": 917897, "vin": [ { "gen": { "height": 917887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81af0dc7e1182e1650b87fbc2d45dbdd56e0222abdff6333632a0215d0ae8eaa" } } ], "extra": [ 1, 207, 79, 243, 57, 169, 85, 163, 65, 98, 205, 141, 160, 168, 94, 78, 95, 161, 66, 185, 187, 98, 131, 19, 0, 64, 26, 67, 154, 195, 201, 157, 93, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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