Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f6a4aad1e0be26605bf72dba34ccb5aa5fc3855b02ea3d9741470616f0bc53

Tx prefix hash: 79219804ec4af767cacf315dc987dce97515cba2f173d9428227fd7c946900da
Tx public key: 0d0d4beb3851e0aa474b8ef161878dae2e52af64492e87110f0b4cde2de5ab60
Timestamp: 1636916071 Timestamp [UCT]: 2021-11-14 18:54:31 Age [y:d:h:m:s]: 03:048:17:27:06
Block: 374300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813570 RingCT/type: yes/0
Extra: 010d0d4beb3851e0aa474b8ef161878dae2e52af64492e87110f0b4cde2de5ab60021100000022328bb496000000000000000000

1 output(s) for total of 35.301170736000 dcy

stealth address amount amount idx
00: edf501b4aa740b295adcd9e6eae7822e0426f19ad576afecc8deee153961d346 35.301170736000 757674 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": 374310, "vin": [ { "gen": { "height": 374300 } } ], "vout": [ { "amount": 35301170736, "target": { "key": "edf501b4aa740b295adcd9e6eae7822e0426f19ad576afecc8deee153961d346" } } ], "extra": [ 1, 13, 13, 75, 235, 56, 81, 224, 170, 71, 75, 142, 241, 97, 135, 141, 174, 46, 82, 175, 100, 73, 46, 135, 17, 15, 11, 76, 222, 45, 229, 171, 96, 2, 17, 0, 0, 0, 34, 50, 139, 180, 150, 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