Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1ecbd6935af560f87fbc717c7d877758d9f7f7656f18b76abd5762e497e6de

Tx prefix hash: 56a990d10394e759848d2d0a1eebd72b41b814a4a4d430e7594ffca45fc7e32d
Tx public key: 685d648d92c3bc36de71809f000b48acd8342fae38f3e1e9d57ab01ae6a81b3b
Timestamp: 1680300053 Timestamp [UCT]: 2023-03-31 22:00:53 Age [y:d:h:m:s]: 01:294:16:15:01
Block: 729324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471436 RingCT/type: yes/0
Extra: 01685d648d92c3bc36de71809f000b48acd8342fae38f3e1e9d57ab01ae6a81b3b0211000000035029cbac000000000000000000

1 output(s) for total of 2.352052789000 dcy

stealth address amount amount idx
00: b9bb9a5f9414dd50686a5c6891d3e800550084cf8184616015979257dd278b1e 2.352052789000 1174831 of 0

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": 729334, "vin": [ { "gen": { "height": 729324 } } ], "vout": [ { "amount": 2352052789, "target": { "key": "b9bb9a5f9414dd50686a5c6891d3e800550084cf8184616015979257dd278b1e" } } ], "extra": [ 1, 104, 93, 100, 141, 146, 195, 188, 54, 222, 113, 128, 159, 0, 11, 72, 172, 216, 52, 47, 174, 56, 243, 225, 233, 213, 122, 176, 26, 230, 168, 27, 59, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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