Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12a0e77930ec1fbc834f3dac456a354f9fbed223a37f3a7e46f0ac361afd6b5f

Tx prefix hash: 982ddc9bd2efa1a0a9e70b67778ee6d9f39800657262288880b8d569fe51465f
Tx public key: b5b82d9d45107f818aa7f90574b43e00f83c99a971a10fae7a34e1632ca81fe7
Timestamp: 1735996550 Timestamp [UCT]: 2025-01-04 13:15:50 Age [y:d:h:m:s]: 00:096:05:42:01
Block: 1190046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68560 RingCT/type: yes/0
Extra: 01b5b82d9d45107f818aa7f90574b43e00f83c99a971a10fae7a34e1632ca81fe702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6ff7aac35cd6d888342efaab9ce1f5c0d5a736254147cc98eb33dd411ce4e2 0.600000000000 1676561 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": 1190056, "vin": [ { "gen": { "height": 1190046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6ff7aac35cd6d888342efaab9ce1f5c0d5a736254147cc98eb33dd411ce4e2" } } ], "extra": [ 1, 181, 184, 45, 157, 69, 16, 127, 129, 138, 167, 249, 5, 116, 180, 62, 0, 248, 60, 153, 169, 113, 161, 15, 174, 122, 52, 225, 99, 44, 168, 31, 231, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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