Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 492e1a03dbb59244dac11a07cb59a6a365c33ea081fce5f812209aa02fbcc73c

Tx prefix hash: 2bf46b971f6821405c9240d5b4e6b7aad1198dccde6899fac0cc3a6b4c3b96f6
Tx public key: a5e5ceeaf33496ecde087b261a4716e9cd0e801865977287dbe8ea5ab26903df
Timestamp: 1614133164 Timestamp [UCT]: 2021-02-24 02:19:24 Age [y:d:h:m:s]: 03:347:17:35:36
Block: 205364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1007487 RingCT/type: yes/0
Extra: 01a5e5ceeaf33496ecde087b261a4716e9cd0e801865977287dbe8ea5ab26903df0211000000364ea414e5000000000000000000

1 output(s) for total of 128.098614541000 dcy

stealth address amount amount idx
00: 4f30c436c7ab4a35d76ffca674bcbd4842156329b1e31eaf356c9ee24f4c1fc3 128.098614541000 419564 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": 205374, "vin": [ { "gen": { "height": 205364 } } ], "vout": [ { "amount": 128098614541, "target": { "key": "4f30c436c7ab4a35d76ffca674bcbd4842156329b1e31eaf356c9ee24f4c1fc3" } } ], "extra": [ 1, 165, 229, 206, 234, 243, 52, 150, 236, 222, 8, 123, 38, 26, 71, 22, 233, 205, 14, 128, 24, 101, 151, 114, 135, 219, 232, 234, 90, 178, 105, 3, 223, 2, 17, 0, 0, 0, 54, 78, 164, 20, 229, 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