Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb964c604635928232ccbdc482e075c5fb705afaec8e0ecec05839cb7d8aed5c

Tx prefix hash: 2f7aa24e62f8b4dc60d9f57076af24219a0e8d858920fc378a7162486e302ff0
Tx public key: 75674165113f46ec0b1daec933fd0bcaf8f9672e8d4e0896edd6ae1f9dbfad30
Timestamp: 1618034382 Timestamp [UCT]: 2021-04-10 05:59:42 Age [y:d:h:m:s]: 03:222:16:57:27
Block: 236616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 919383 RingCT/type: yes/0
Extra: 0175674165113f46ec0b1daec933fd0bcaf8f9672e8d4e0896edd6ae1f9dbfad300211000000870dc70aa7000000000000000000

1 output(s) for total of 100.925527658000 dcy

stealth address amount amount idx
00: f1913be84790c2290a393fe8493b1dad626fc3ea504f0f4a70acb5753fd8a993 100.925527658000 492146 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": 236626, "vin": [ { "gen": { "height": 236616 } } ], "vout": [ { "amount": 100925527658, "target": { "key": "f1913be84790c2290a393fe8493b1dad626fc3ea504f0f4a70acb5753fd8a993" } } ], "extra": [ 1, 117, 103, 65, 101, 17, 63, 70, 236, 11, 29, 174, 201, 51, 253, 11, 202, 248, 249, 103, 46, 141, 78, 8, 150, 237, 214, 174, 31, 157, 191, 173, 48, 2, 17, 0, 0, 0, 135, 13, 199, 10, 167, 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