Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3573719a9fcdf0f120028e30dacc26cf36564968b47814f4665b50893113afc

Tx prefix hash: 490a93f7900f967b399b1c14f382072df0a59e0c9a20dbd107ae0b7678b8f6c0
Tx public key: 4197d9adb5ec0ca80ca6ed4846303c9346ff4827999c09a7e887e403b12aa29d
Timestamp: 1625460962 Timestamp [UCT]: 2021-07-05 04:56:02 Age [y:d:h:m:s]: 04:127:22:24:25
Block: 288461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119627 RingCT/type: yes/0
Extra: 014197d9adb5ec0ca80ca6ed4846303c9346ff4827999c09a7e887e403b12aa29d02110000000bb8178fc1000000000000000000

1 output(s) for total of 67.953130428000 dcy

stealth address amount amount idx
00: b60b61e50cf816717be77e91b234baaa9f9404ed57e96eae38e694f47b0a159d 67.953130428000 604360 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": 288471, "vin": [ { "gen": { "height": 288461 } } ], "vout": [ { "amount": 67953130428, "target": { "key": "b60b61e50cf816717be77e91b234baaa9f9404ed57e96eae38e694f47b0a159d" } } ], "extra": [ 1, 65, 151, 217, 173, 181, 236, 12, 168, 12, 166, 237, 72, 70, 48, 60, 147, 70, 255, 72, 39, 153, 156, 9, 167, 232, 135, 228, 3, 177, 42, 162, 157, 2, 17, 0, 0, 0, 11, 184, 23, 143, 193, 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