Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4f1f4b6f78055e5208f3695bb28f503382e91f7476a6a4f4d586138f9748b7

Tx prefix hash: 557f4e315b3b9b4558c5075ace78a7a6ddea71334e90f55df1b81dd6126e53fe
Tx public key: 6c3746b3f889d1b22d8ae1fb06dc709f324c20e0ca0b84bf9140f2531063876c
Timestamp: 1653670779 Timestamp [UCT]: 2022-05-27 16:59:39 Age [y:d:h:m:s]: 02:189:21:31:29
Block: 510139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656329 RingCT/type: yes/0
Extra: 016c3746b3f889d1b22d8ae1fb06dc709f324c20e0ca0b84bf9140f2531063876c02110000000475e3f0e9000000000000000000

1 output(s) for total of 12.522698223000 dcy

stealth address amount amount idx
00: 2a7eb455dd2941ea9335ef8a22202cb911d4cd29c6e9854871f3e38b6dd75ae4 12.522698223000 936424 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": 510149, "vin": [ { "gen": { "height": 510139 } } ], "vout": [ { "amount": 12522698223, "target": { "key": "2a7eb455dd2941ea9335ef8a22202cb911d4cd29c6e9854871f3e38b6dd75ae4" } } ], "extra": [ 1, 108, 55, 70, 179, 248, 137, 209, 178, 45, 138, 225, 251, 6, 220, 112, 159, 50, 76, 32, 224, 202, 11, 132, 191, 145, 64, 242, 83, 16, 99, 135, 108, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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