Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1b5a0eb261a4e11521fed4f2608e8d453100d5c4f57f0846ca1552a69f1e4f

Tx prefix hash: 441f8250e2072efbc629489e186539a74da4bb9fa8812d98bb77527e0dbbc69e
Tx public key: 915191156cbb469d8d57c41bd875a4719bb158ceb4c5f347842b36e243af9b5b
Timestamp: 1713742845 Timestamp [UCT]: 2024-04-21 23:40:45 Age [y:d:h:m:s]: 00:350:17:23:30
Block: 1005673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250719 RingCT/type: yes/0
Extra: 01915191156cbb469d8d57c41bd875a4719bb158ceb4c5f347842b36e243af9b5b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99309207bb92689e81928f91ddd6c3ed4fa6bd1b9f48c4f0b4c2f65bc70a7675 0.600000000000 1466435 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": 1005683, "vin": [ { "gen": { "height": 1005673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99309207bb92689e81928f91ddd6c3ed4fa6bd1b9f48c4f0b4c2f65bc70a7675" } } ], "extra": [ 1, 145, 81, 145, 21, 108, 187, 70, 157, 141, 87, 196, 27, 216, 117, 164, 113, 155, 177, 88, 206, 180, 197, 243, 71, 132, 43, 54, 226, 67, 175, 155, 91, 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