Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002b75b9a1125711e27a6ca8432c489a57556f87c670ed43e0e7700908bd3228

Tx prefix hash: 8d38d1940f4f0d54a85ba0ff7e272e0594e610c2a27b29288c2611fe38f5e774
Tx public key: c1f1f04a7b5bb52f85a67f37686a6e494c61558665351db6a7a6c6c4dd3ec0f4
Timestamp: 1717957727 Timestamp [UCT]: 2024-06-09 18:28:47 Age [y:d:h:m:s]: 00:229:05:16:30
Block: 1040627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163988 RingCT/type: yes/0
Extra: 01c1f1f04a7b5bb52f85a67f37686a6e494c61558665351db6a7a6c6c4dd3ec0f40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79cfb2f00ae6e2d5ed5ca3382a460642e02f9122521217a92deb479b5633142d 0.600000000000 1509284 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": 1040637, "vin": [ { "gen": { "height": 1040627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79cfb2f00ae6e2d5ed5ca3382a460642e02f9122521217a92deb479b5633142d" } } ], "extra": [ 1, 193, 241, 240, 74, 123, 91, 181, 47, 133, 166, 127, 55, 104, 106, 110, 73, 76, 97, 85, 134, 101, 53, 29, 182, 167, 166, 198, 196, 221, 62, 192, 244, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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