Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f9f487937e9b81ce93a4d2af609f4f4ab99cf3453239cd309c5089de504e981

Tx prefix hash: 508346c639722dcda49618dbc120d90332ac3ad67b870658fd69d38c21a713ed
Tx public key: 4d5e17b8db27a613571a0ed9f0316c992fc44de54b2c3742b9c2c60b734a5b97
Timestamp: 1740848929 Timestamp [UCT]: 2025-03-01 17:08:49 Age [y:d:h:m:s]: 00:265:01:17:51
Block: 1229940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187188 RingCT/type: yes/0
Extra: 014d5e17b8db27a613571a0ed9f0316c992fc44de54b2c3742b9c2c60b734a5b97021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9879e790d4c5a4e8639f0048594ac58075c8bd67b583e70f2441b3f8186a72d0 0.600000000000 1716831 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": 1229950, "vin": [ { "gen": { "height": 1229940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9879e790d4c5a4e8639f0048594ac58075c8bd67b583e70f2441b3f8186a72d0" } } ], "extra": [ 1, 77, 94, 23, 184, 219, 39, 166, 19, 87, 26, 14, 217, 240, 49, 108, 153, 47, 196, 77, 229, 75, 44, 55, 66, 185, 194, 198, 11, 115, 74, 91, 151, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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