Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996e90a47144be3b73f3f9cee39d8208a4e621d01afebae47146174f8a24fbe7

Tx prefix hash: 43fda00fe5f960d4bb17aa856b34333fa9330cccdc94bb5bc3588afdcfd1a7eb
Tx public key: c0b4bd1e0bf10a23253b9237af44e7d3aa21440b6eef6ac31e57c180792a8fa4
Timestamp: 1702894648 Timestamp [UCT]: 2023-12-18 10:17:28 Age [y:d:h:m:s]: 01:149:11:32:39
Block: 915737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367993 RingCT/type: yes/0
Extra: 01c0b4bd1e0bf10a23253b9237af44e7d3aa21440b6eef6ac31e57c180792a8fa402110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 001e8f8b36129d1e91dbc1a5f0dfa72ffcbe8d8207bab0f663439abf4e9e4f06 0.600000000000 1373161 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": 915747, "vin": [ { "gen": { "height": 915737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001e8f8b36129d1e91dbc1a5f0dfa72ffcbe8d8207bab0f663439abf4e9e4f06" } } ], "extra": [ 1, 192, 180, 189, 30, 11, 241, 10, 35, 37, 59, 146, 55, 175, 68, 231, 211, 170, 33, 68, 11, 110, 239, 106, 195, 30, 87, 193, 128, 121, 42, 143, 164, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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