Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e77d020031d7d27f4409506f219f515d870cae55db674f10443449a5b8d9e1

Tx prefix hash: 2afa64ad68e454627a0c1f3fc120847232f0220d564600dfd30b1ee424bc95d4
Tx public key: c21afe6aa6d7edd6f6b61cd3e7c0c280745058f5530bd74513fb893786508f63
Timestamp: 1728415593 Timestamp [UCT]: 2024-10-08 19:26:33 Age [y:d:h:m:s]: 00:157:10:34:26
Block: 1127323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112318 RingCT/type: yes/0
Extra: 01c21afe6aa6d7edd6f6b61cd3e7c0c280745058f5530bd74513fb893786508f63021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d4d531077e6f0643f04ac524ac3ee624b0c867b77796b53ba6b75c7fcabadab 0.600000000000 1610126 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": 1127333, "vin": [ { "gen": { "height": 1127323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d4d531077e6f0643f04ac524ac3ee624b0c867b77796b53ba6b75c7fcabadab" } } ], "extra": [ 1, 194, 26, 254, 106, 166, 215, 237, 214, 246, 182, 28, 211, 231, 192, 194, 128, 116, 80, 88, 245, 83, 11, 215, 69, 19, 251, 137, 55, 134, 80, 143, 99, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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