Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f8b78ae4f8706ae7956867be6830008cc5c24a4d81594221ee3a1cc7698eb43

Tx prefix hash: c5c2011d09c09b1ed2cd4d6719ea0c507703fbb0ac353214bcd3115ff9f077cf
Tx public key: bb2083e05b12099e6da8eb2802f834d1ff0dddb8d3a404db4dbef3cab5f355c2
Timestamp: 1708160829 Timestamp [UCT]: 2024-02-17 09:07:09 Age [y:d:h:m:s]: 01:038:05:42:15
Block: 959394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288346 RingCT/type: yes/0
Extra: 01bb2083e05b12099e6da8eb2802f834d1ff0dddb8d3a404db4dbef3cab5f355c20211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5688a86d2a10569b9ddaea57e3d4f7eee03511ef0c8f85fa60bdc0d06e500fd 0.600000000000 1418929 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": 959404, "vin": [ { "gen": { "height": 959394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5688a86d2a10569b9ddaea57e3d4f7eee03511ef0c8f85fa60bdc0d06e500fd" } } ], "extra": [ 1, 187, 32, 131, 224, 91, 18, 9, 158, 109, 168, 235, 40, 2, 248, 52, 209, 255, 13, 221, 184, 211, 164, 4, 219, 77, 190, 243, 202, 181, 243, 85, 194, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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