Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59019fea8c29d7c0c97215eeee0f18fca9984427f11f1e6758866c0b1c8bbbce

Tx prefix hash: 658edcd05f2e660d34ef7cda2976b4c6708f79f158e641c6e7683a1a0f6ef6cf
Tx public key: cd6f6d0e20b2cd617a87e99abfb0701c3b6395a01b1817599b00d650c052329a
Timestamp: 1692706591 Timestamp [UCT]: 2023-08-22 12:16:31 Age [y:d:h:m:s]: 01:147:01:17:56
Block: 831444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366475 RingCT/type: yes/0
Extra: 01cd6f6d0e20b2cd617a87e99abfb0701c3b6395a01b1817599b00d650c052329a02110000001075e3f0e9000000000000000000

1 output(s) for total of 1.079147883000 dcy

stealth address amount amount idx
00: 0f44c0dcef69de951d2f1ca16c1ced4faaf2c5d4f2a4bd6c587546c16bfe1b38 1.079147883000 1283868 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": 831454, "vin": [ { "gen": { "height": 831444 } } ], "vout": [ { "amount": 1079147883, "target": { "key": "0f44c0dcef69de951d2f1ca16c1ced4faaf2c5d4f2a4bd6c587546c16bfe1b38" } } ], "extra": [ 1, 205, 111, 109, 14, 32, 178, 205, 97, 122, 135, 233, 154, 191, 176, 112, 28, 59, 99, 149, 160, 27, 24, 23, 89, 155, 0, 214, 80, 192, 82, 50, 154, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 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