Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3a24c7edd8b2d821b4156f41fa2fcafb2cdbe0c80dc328ae326963f5a9645e

Tx prefix hash: 2e1a2bca43d2c02f5f39c565d5f2c8a009eacf85631a846818b8a7d4da3007b9
Tx public key: 1777cda60c0212ad714b0413d221733c2fb2574f66338b2864c31287a3afb7cb
Timestamp: 1583452720 Timestamp [UCT]: 2020-03-05 23:58:40 Age [y:d:h:m:s]: 05:244:07:07:19
Block: 77075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1327551 RingCT/type: yes/0
Extra: 011777cda60c0212ad714b0413d221733c2fb2574f66338b2864c31287a3afb7cb02110000000a4943cd9f000000000000000000

1 output(s) for total of 340.893973707000 dcy

stealth address amount amount idx
00: 6112ca2643fb77da6381d97b468a8f9b377d915e1c533df10483eb0ec5002022 340.893973707000 141911 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": 77085, "vin": [ { "gen": { "height": 77075 } } ], "vout": [ { "amount": 340893973707, "target": { "key": "6112ca2643fb77da6381d97b468a8f9b377d915e1c533df10483eb0ec5002022" } } ], "extra": [ 1, 23, 119, 205, 166, 12, 2, 18, 173, 113, 75, 4, 19, 210, 33, 115, 60, 47, 178, 87, 79, 102, 51, 139, 40, 100, 195, 18, 135, 163, 175, 183, 203, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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