Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8585d8fefc6252539f4f40b21f06afbf6d38c3b2000440c15fd4cb3d0ef418

Tx prefix hash: cb2be5a61d927b6c3e794606cc28fad53b44749cdda2edbc86a03274787ed77a
Tx public key: 611ec9da857704a2b50cfafdc986c7b7d26da1c08dbd930fde45c53f0968f9b3
Timestamp: 1737924746 Timestamp [UCT]: 2025-01-26 20:52:26 Age [y:d:h:m:s]: 00:141:10:59:53
Block: 1205908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100901 RingCT/type: yes/0
Extra: 01611ec9da857704a2b50cfafdc986c7b7d26da1c08dbd930fde45c53f0968f9b3021100000051007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ad09f2f6853ac6c02915154634d683791ab7f9b8dd93e5ccd3538b4b9c40425 0.600000000000 1692607 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": 1205918, "vin": [ { "gen": { "height": 1205908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad09f2f6853ac6c02915154634d683791ab7f9b8dd93e5ccd3538b4b9c40425" } } ], "extra": [ 1, 97, 30, 201, 218, 133, 119, 4, 162, 181, 12, 250, 253, 201, 134, 199, 183, 210, 109, 161, 192, 141, 189, 147, 15, 222, 69, 197, 63, 9, 104, 249, 179, 2, 17, 0, 0, 0, 81, 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