Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544b9681ba0e3f4fccd28c58cd1a87d46b3c855cbabc5e066834a175b2a2e6be

Tx prefix hash: f3baf6e6fb455edbeb9001c88a0f862821d56ce0047bfbeec9340776588045f4
Tx public key: 8717a9b3f3219ac358f12c3c3fe0528ec76e88388569d1f39cfcef5fb970c824
Timestamp: 1702544149 Timestamp [UCT]: 2023-12-14 08:55:49 Age [y:d:h:m:s]: 01:327:10:06:28
Block: 912833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492854 RingCT/type: yes/0
Extra: 018717a9b3f3219ac358f12c3c3fe0528ec76e88388569d1f39cfcef5fb970c82402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7415187d9de5e6fb22460064ea5cad8c4f53a994ddfa5666d4bcefa17bb5a89f 0.600000000000 1370069 of 15

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": 912843, "vin": [ { "gen": { "height": 912833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7415187d9de5e6fb22460064ea5cad8c4f53a994ddfa5666d4bcefa17bb5a89f" } } ], "extra": [ 1, 135, 23, 169, 179, 243, 33, 154, 195, 88, 241, 44, 60, 63, 224, 82, 142, 199, 110, 136, 56, 133, 105, 209, 243, 156, 252, 239, 95, 185, 112, 200, 36, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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