Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 863d5f77dd973127060fdf5e5d18580d2e60bf49cb32a682b07d73a111443fdd

Tx prefix hash: f37714d0a14830ec0b8f685efbb6e7e040eafadef28f14a793f1b58a2b5c73ca
Tx public key: a6cfd184cc8cf7298a6deae11ae0ef3104c632d33988a3f0ea67fca134d9c18a
Timestamp: 1686529477 Timestamp [UCT]: 2023-06-12 00:24:37 Age [y:d:h:m:s]: 01:361:09:00:32
Block: 780334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519487 RingCT/type: yes/0
Extra: 01a6cfd184cc8cf7298a6deae11ae0ef3104c632d33988a3f0ea67fca134d9c18a02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.593784815000 dcy

stealth address amount amount idx
00: a2f79b9af25157adfe9235d11458772611ee5e2f4f25eaa98e0f05a11b0b2b54 1.593784815000 1230037 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": 780344, "vin": [ { "gen": { "height": 780334 } } ], "vout": [ { "amount": 1593784815, "target": { "key": "a2f79b9af25157adfe9235d11458772611ee5e2f4f25eaa98e0f05a11b0b2b54" } } ], "extra": [ 1, 166, 207, 209, 132, 204, 140, 247, 41, 138, 109, 234, 225, 26, 224, 239, 49, 4, 198, 50, 211, 57, 136, 163, 240, 234, 103, 252, 161, 52, 217, 193, 138, 2, 17, 0, 0, 0, 2, 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