Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e860e74b28998e79be67693a362c0ef9f77b13c3620e6d01bddefc74b8b8a1e

Tx prefix hash: 047eb8a84d9b47c801f3115424e4f75a5ffe863f8e9de645e32d9d55cb8feadf
Tx public key: 0aab9d98fd0a71d32d38a6d7a79199042ffde29ca4f4db58332b676bbd75d997
Timestamp: 1710976287 Timestamp [UCT]: 2024-03-20 23:11:27 Age [y:d:h:m:s]: 01:005:09:34:30
Block: 982764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264800 RingCT/type: yes/0
Extra: 010aab9d98fd0a71d32d38a6d7a79199042ffde29ca4f4db58332b676bbd75d9970211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cf16c6804301be15d905aa2eb7afc586a63ca74bcfd1dcc359bb347a798a515 0.600000000000 1442875 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": 982774, "vin": [ { "gen": { "height": 982764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cf16c6804301be15d905aa2eb7afc586a63ca74bcfd1dcc359bb347a798a515" } } ], "extra": [ 1, 10, 171, 157, 152, 253, 10, 113, 211, 45, 56, 166, 215, 167, 145, 153, 4, 47, 253, 226, 156, 164, 244, 219, 88, 51, 43, 103, 107, 189, 117, 217, 151, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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