Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62166a2716af99b8d6796fc7538e0ad5f8f13c35181678cf224f16123a1d80f1

Tx prefix hash: 9766467dfdbffd0f97e1dffa8088d8ba556d38ba2cc8f6aee14da2e807a920aa
Tx public key: a4ae9eb43475a5945f5ef1eb4c4ceb0810873d18be0350347b26dc888602ffe4
Timestamp: 1588734388 Timestamp [UCT]: 2020-05-06 03:06:28 Age [y:d:h:m:s]: 05:019:13:59:31
Block: 98733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1191304 RingCT/type: yes/0
Extra: 01a4ae9eb43475a5945f5ef1eb4c4ceb0810873d18be0350347b26dc888602ffe402110000000486362411000000000000000000

1 output(s) for total of 288.973054634000 dcy

stealth address amount amount idx
00: fea25ff5ac63cac3adb11d5f22fbbdfabe3c960f3d984aeead69bf9a12140430 288.973054634000 174471 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": 98743, "vin": [ { "gen": { "height": 98733 } } ], "vout": [ { "amount": 288973054634, "target": { "key": "fea25ff5ac63cac3adb11d5f22fbbdfabe3c960f3d984aeead69bf9a12140430" } } ], "extra": [ 1, 164, 174, 158, 180, 52, 117, 165, 148, 95, 94, 241, 235, 76, 76, 235, 8, 16, 135, 61, 24, 190, 3, 80, 52, 123, 38, 220, 136, 134, 2, 255, 228, 2, 17, 0, 0, 0, 4, 134, 54, 36, 17, 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