Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677670ff65902970fec0a1c4fe29c7dd14cafc48f930acec2c539c7f361afc40

Tx prefix hash: a860b57686f9c76391353b6501cf7da16d40a940c1a2c281250e5fb7aee23825
Tx public key: 54e1922da1a271c99f1dcaf81cb135bd79f4079dd3411e3554bde0b0099a845f
Timestamp: 1578428379 Timestamp [UCT]: 2020-01-07 20:19:39 Age [y:d:h:m:s]: 04:327:19:12:42
Block: 40752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123604 RingCT/type: yes/0
Extra: 0154e1922da1a271c99f1dcaf81cb135bd79f4079dd3411e3554bde0b0099a845f021100000008d81c26c0000000000000000000

1 output(s) for total of 449.751430723000 dcy

stealth address amount amount idx
00: fa4a3e06bca6bfd852e4b1b6c0f80f3335ad2b6b4f2a7cfb6ec6622cb80db5ad 449.751430723000 71879 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": 40762, "vin": [ { "gen": { "height": 40752 } } ], "vout": [ { "amount": 449751430723, "target": { "key": "fa4a3e06bca6bfd852e4b1b6c0f80f3335ad2b6b4f2a7cfb6ec6622cb80db5ad" } } ], "extra": [ 1, 84, 225, 146, 45, 161, 162, 113, 201, 159, 29, 202, 248, 28, 177, 53, 189, 121, 244, 7, 157, 211, 65, 30, 53, 84, 189, 224, 176, 9, 154, 132, 95, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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