Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac1c7d655a7d4d86f99448e451a1b9afc7183d1800ade12e53ecc3520059e659

Tx prefix hash: 810753066a1fa6aeb1d6c4cbbb907ef13aa35fc6a1a4f84aba96d5f997b1eea2
Tx public key: 07af2a300466fd210c5d04008757c4bf4c49f8cdb3706afb3621151087a55278
Timestamp: 1695474534 Timestamp [UCT]: 2023-09-23 13:08:54 Age [y:d:h:m:s]: 01:228:10:18:09
Block: 854426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424337 RingCT/type: yes/0
Extra: 0107af2a300466fd210c5d04008757c4bf4c49f8cdb3706afb3621151087a55278021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.905590844000 dcy

stealth address amount amount idx
00: 3bbd3d1f9ffab6bb4d914637ac60fdb43ba17b514f8182b32c221594f77422fd 0.905590844000 1308398 of 0

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": 854436, "vin": [ { "gen": { "height": 854426 } } ], "vout": [ { "amount": 905590844, "target": { "key": "3bbd3d1f9ffab6bb4d914637ac60fdb43ba17b514f8182b32c221594f77422fd" } } ], "extra": [ 1, 7, 175, 42, 48, 4, 102, 253, 33, 12, 93, 4, 0, 135, 87, 196, 191, 76, 73, 248, 205, 179, 112, 106, 251, 54, 33, 21, 16, 135, 165, 82, 120, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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