Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88d47d3f2eff23dace6b722d7c9785499d8fdaae368184cc3a42b112c88ff91e

Tx prefix hash: f113ac9608bcfe7ff2f09a283a8826d0b19d626c5d9fc839f0dc51b5288a374b
Tx public key: ee0ef80b7dbd0f9e3308e7242952d4f50ddb78f044c514db14d77060a8adf455
Timestamp: 1704236037 Timestamp [UCT]: 2024-01-02 22:53:57 Age [y:d:h:m:s]: 01:318:15:19:48
Block: 926856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486563 RingCT/type: yes/0
Extra: 01ee0ef80b7dbd0f9e3308e7242952d4f50ddb78f044c514db14d77060a8adf4550211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a837533bf7c1195f4840722a14481f345534944a5d6aba5965303c224df1d4a 0.600000000000 1384654 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": 926866, "vin": [ { "gen": { "height": 926856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a837533bf7c1195f4840722a14481f345534944a5d6aba5965303c224df1d4a" } } ], "extra": [ 1, 238, 14, 248, 11, 125, 189, 15, 158, 51, 8, 231, 36, 41, 82, 212, 245, 13, 219, 120, 240, 68, 197, 20, 219, 20, 215, 112, 96, 168, 173, 244, 85, 2, 17, 0, 0, 0, 3, 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