Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96107f8e7483988ed601aa93ef5c1c03924d989c20f2b5fe2fa9e25968fa1255

Tx prefix hash: f1fc4a37368f4d7486274efa18288415c262ec6a6439b3f69e738549c954a3dd
Tx public key: 53201619850b2268a7e582a99cec8589dd2cbfa79cb1a66c70900a3ccbab509c
Timestamp: 1698687939 Timestamp [UCT]: 2023-10-30 17:45:39 Age [y:d:h:m:s]: 01:151:02:06:05
Block: 881085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368967 RingCT/type: yes/0
Extra: 0153201619850b2268a7e582a99cec8589dd2cbfa79cb1a66c70900a3ccbab509c021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.738923792000 dcy

stealth address amount amount idx
00: a4168d3351db63a152598645e7a971aeec4f68893d34ed5da5bfb08951c1cf16 0.738923792000 1336657 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": 881095, "vin": [ { "gen": { "height": 881085 } } ], "vout": [ { "amount": 738923792, "target": { "key": "a4168d3351db63a152598645e7a971aeec4f68893d34ed5da5bfb08951c1cf16" } } ], "extra": [ 1, 83, 32, 22, 25, 133, 11, 34, 104, 167, 229, 130, 169, 156, 236, 133, 137, 221, 44, 191, 167, 156, 177, 166, 108, 112, 144, 10, 60, 203, 171, 80, 156, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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