Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f205e2dac87afdf9a9b531e4d874801ddf8498c2ad4983d9e151b83498d113

Tx prefix hash: 36c75578ab5cbfa2e42fcccd273af3de64fd6ff643c2a76d44d91ddfba65741b
Tx public key: 814a5d91be073c580954a32571edd0bf88f74928924e9c4d8ded1c366d8c42d2
Timestamp: 1729643023 Timestamp [UCT]: 2024-10-23 00:23:43 Age [y:d:h:m:s]: 00:200:15:08:22
Block: 1137472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143210 RingCT/type: yes/0
Extra: 01814a5d91be073c580954a32571edd0bf88f74928924e9c4d8ded1c366d8c42d202110000000192627dee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f7d58ac8ef2fee4b0372c141e4bbbb8b19a6d9658b5e223f9efc891bf317843 0.600000000000 1620971 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": 1137482, "vin": [ { "gen": { "height": 1137472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f7d58ac8ef2fee4b0372c141e4bbbb8b19a6d9658b5e223f9efc891bf317843" } } ], "extra": [ 1, 129, 74, 93, 145, 190, 7, 60, 88, 9, 84, 163, 37, 113, 237, 208, 191, 136, 247, 73, 40, 146, 78, 156, 77, 141, 237, 28, 54, 109, 140, 66, 210, 2, 17, 0, 0, 0, 1, 146, 98, 125, 238, 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