Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709a66967f6fe3dae6e2bc40916e14ba95475257428285abf658a70e343dbddb

Tx prefix hash: 790667b658ce6e4f9622157479080f59d3bd6c2c8058979bd091aed8f8d125d0
Tx public key: 46875bd94d699324efe02b390a2c5eccc86112ebc616f5e4dfc59ec819707f84
Timestamp: 1696038711 Timestamp [UCT]: 2023-09-30 01:51:51 Age [y:d:h:m:s]: 01:048:08:42:33
Block: 859108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295803 RingCT/type: yes/0
Extra: 0146875bd94d699324efe02b390a2c5eccc86112ebc616f5e4dfc59ec819707f84021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.873813211000 dcy

stealth address amount amount idx
00: c691d27c5f8025fa1ec8dc52bb31e784c0080c1c6c99d732eb49c0b7d998dd3c 0.873813211000 1313318 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": 859118, "vin": [ { "gen": { "height": 859108 } } ], "vout": [ { "amount": 873813211, "target": { "key": "c691d27c5f8025fa1ec8dc52bb31e784c0080c1c6c99d732eb49c0b7d998dd3c" } } ], "extra": [ 1, 70, 135, 91, 217, 77, 105, 147, 36, 239, 224, 43, 57, 10, 44, 94, 204, 200, 97, 18, 235, 198, 22, 245, 228, 223, 197, 158, 200, 25, 112, 127, 132, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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