Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161e25a58cceef46c5c7e9923a424624d2f236f2a000a2f9462002fb9ffc2272

Tx prefix hash: c96b6d9bdcf76d4e88bb42f77c681d2cc5de6e51dc91904b44e782229ef586d1
Tx public key: 26035d78f3d3c22727d9e0ab88246cf957cc98325e538064a4646693261303ba
Timestamp: 1705116719 Timestamp [UCT]: 2024-01-13 03:31:59 Age [y:d:h:m:s]: 01:086:08:31:05
Block: 934140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322820 RingCT/type: yes/0
Extra: 0126035d78f3d3c22727d9e0ab88246cf957cc98325e538064a4646693261303ba02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc32ad9d877d32d850aee548cdf940a212a5ffd1ebb08c41f68e754c3c6a21dd 0.600000000000 1392128 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": 934150, "vin": [ { "gen": { "height": 934140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc32ad9d877d32d850aee548cdf940a212a5ffd1ebb08c41f68e754c3c6a21dd" } } ], "extra": [ 1, 38, 3, 93, 120, 243, 211, 194, 39, 39, 217, 224, 171, 136, 36, 108, 249, 87, 204, 152, 50, 94, 83, 128, 100, 164, 100, 102, 147, 38, 19, 3, 186, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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