Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3118fadb928d8547e737a78253a1158aff3b9e21eb6a18e6d18b8bf2ef266510

Tx prefix hash: 672db3a4aad1ea1b9c5ae2149771377d7777e9fac9f36ab65518cf82a381e98f
Tx public key: 78d96b8dd613bc286768363d2e0fddf752bd8a7b14f4f59c914123f923b2001a
Timestamp: 1580793239 Timestamp [UCT]: 2020-02-04 05:13:59 Age [y:d:h:m:s]: 05:097:20:15:53
Block: 58365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221894 RingCT/type: yes/0
Extra: 0178d96b8dd613bc286768363d2e0fddf752bd8a7b14f4f59c914123f923b2001a0211000000032264afe6000000000000000000

1 output(s) for total of 393.199853422000 dcy

stealth address amount amount idx
00: d55a300e1b414f576f655d0fea795847622c4a85128d052392a698bf37a24330 393.199853422000 107841 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": 58375, "vin": [ { "gen": { "height": 58365 } } ], "vout": [ { "amount": 393199853422, "target": { "key": "d55a300e1b414f576f655d0fea795847622c4a85128d052392a698bf37a24330" } } ], "extra": [ 1, 120, 217, 107, 141, 214, 19, 188, 40, 103, 104, 54, 61, 46, 15, 221, 247, 82, 189, 138, 123, 20, 244, 245, 156, 145, 65, 35, 249, 35, 178, 0, 26, 2, 17, 0, 0, 0, 3, 34, 100, 175, 230, 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