Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79fa7a92a137d10053b02c14d9ae21b7f54f683dd0a96182832bb922e5581c50

Tx prefix hash: 7bf668d6edabee443e8c7f529ae788610908b6ab2d281b7604be1ef013c13151
Tx public key: 706d870648d49dc67b3527f1b47aa266bf1b22e5443da728843113b41e2e800c
Timestamp: 1597894013 Timestamp [UCT]: 2020-08-20 03:26:53 Age [y:d:h:m:s]: 04:092:21:32:07
Block: 128708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1028778 RingCT/type: yes/0
Extra: 01706d870648d49dc67b3527f1b47aa266bf1b22e5443da728843113b41e2e800c0211000000054943cd9f000000000000000000

1 output(s) for total of 229.899320366000 dcy

stealth address amount amount idx
00: 4810d04976d0c0f865e676366fd598b4854e5411b2a4c10995a6ae263d380c77 229.899320366000 216030 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": 128718, "vin": [ { "gen": { "height": 128708 } } ], "vout": [ { "amount": 229899320366, "target": { "key": "4810d04976d0c0f865e676366fd598b4854e5411b2a4c10995a6ae263d380c77" } } ], "extra": [ 1, 112, 109, 135, 6, 72, 212, 157, 198, 123, 53, 39, 241, 180, 122, 162, 102, 191, 27, 34, 229, 68, 61, 167, 40, 132, 49, 19, 180, 30, 46, 128, 12, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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