Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1718bde09b010d3edbba981d0f276c34d5ad1e5e549c955af949eecd97c24948

Tx prefix hash: 36789eced7e6d1b47b926db85d84a8e2b1bed49e3cd61672e3c9f1ceb758199a
Tx public key: 603b97608c7504decf3387d823012f9eebadc6503cfb8d41b08054d5d3e1faf6
Timestamp: 1708977794 Timestamp [UCT]: 2024-02-26 20:03:14 Age [y:d:h:m:s]: 01:266:18:05:19
Block: 966188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449382 RingCT/type: yes/0
Extra: 01603b97608c7504decf3387d823012f9eebadc6503cfb8d41b08054d5d3e1faf602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d3a038fe4cf2271cc3c39fe91bb4b497b26b3727ccb132bfef3fd93d2de99f2 0.600000000000 1425945 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": 966198, "vin": [ { "gen": { "height": 966188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d3a038fe4cf2271cc3c39fe91bb4b497b26b3727ccb132bfef3fd93d2de99f2" } } ], "extra": [ 1, 96, 59, 151, 96, 140, 117, 4, 222, 207, 51, 135, 216, 35, 1, 47, 158, 235, 173, 198, 80, 60, 251, 141, 65, 176, 128, 84, 213, 211, 225, 250, 246, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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